windowstcpip.info Report : Visit Site


  • Server:nginx...
    X-Powered-By:PHP/5.3.3

    The main IP address: 91.195.61.245,Your server Russian Federation,Kotel'niki ISP:Ugresha Network Ltd.  TLD:info CountryCode:RU

    The description :tcp ip networking, windows network problems, windows ipconfig, windows networking troubleshooting, windows networking tutorials subscribe in a rss 20 jun lan set up problem hello, i am setting up a la...

    This report updates in 20-Jul-2018

Created Date:2010-07-11

Technical data of the windowstcpip.info


Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host windowstcpip.info. Currently, hosted in Russian Federation and its service provider is Ugresha Network Ltd. .

Latitude: 55.635459899902
Longitude: 37.844501495361
Country: Russian Federation (RU)
City: Kotel'niki
Region: Moskva
ISP: Ugresha Network Ltd.

HTTP Header Analysis


HTTP Header information is a part of HTTP protocol that a user's browser sends to called nginx containing the details of what the browser wants and will accept back from the web server.

X-Powered-By:PHP/5.3.3
Transfer-Encoding:chunked
Expires:Sun, 19 Aug 2018 21:23:08 GMT
Server:nginx
Connection:keep-alive
Content-Encoding:gzip
Cache-Control:max-age=2678400
Date:Thu, 19 Jul 2018 21:23:08 GMT
Content-Type:text/html; charset=UTF-8
X-Pingback:http://www.windowstcpip.info/xmlrpc.php

DNS

soa:www.windowstcpip.info. root.www.windowstcpip.info. 2018050600 10800 3600 604800 3600
ns:ns2.windowstcpip.info.
ns1.windowstcpip.info.
ipv4:IP:91.195.61.245
ASN:43595
OWNER:UGRESHA-NET-AS, RU
Country:RU

HtmlToText

tcp ip networking, windows network problems, windows ipconfig, windows networking troubleshooting, windows networking tutorials subscribe in a rss 20 jun lan set up problem hello, i am setting up a lan of 3 pc boxes & 2 unix freebsd’s, smc barricade router & hub. the unix – pc interactions to use samba, no problem expected there, had it set up before. the 3 pc’s, 2 wins2000 professional. & 1 win98. all pc’s shows the correct ip settings from ipconfig, with respect to ip address; subnet mask & default gateway. i can ping from each to each with a typical < 10 ms signal return. a "tracert" shows again < 10 ms signal to target machine in 1 hop the problem : despite this apparent symmetrical interaction, one of the win2000 machine does not share it’s files with the otherwin2000 machine, but shares files with the win98 pc. off course file sharing is set for all disks, could someone identify the problem and a fix. thanks – adam – ps: pl. reply to group . comments (2) 20 jun adventures with closesocket() hi, i know this has been a problem for people in the past, but i’ll see if anyone has any new ideas. basically if i write an extremely simple server that simply sends back about ~40k of data back to the client and then closes the socket, then the connection is closed before sending all the data. if i add the following code before closing: fd_set fds; fd_zero(&fds); fd_set(m_handle, &fds); sleep(0); ::select(m_handle + 1, 0, &fds, 0, 0); sleep(0); shutdown(m_handle, sd_send); sleep(0); ::closesocket(m_handle); i can get ie to receive the entire data, but telnet doesn’t (this is on w2k btw). if i remove a single line of code from above it stops working for ie. i’ve tried every possible linger option with no luck. i’ve tried wsaeventselect on fd_close, no luck. the only thing that works for telnet is a hard-coded sleep for a considerable period (4-5 seconds). now it may be a bug in telnet: if i telnet to iis and retrieve a document of a similar size, then data is also lost (providing you don’t have connection: keep-alive). i’ve never seen this problem with ie but it still seems strange i need so much code just to get a graceful socket closure. any clues? dylan comment (1) 20 jun how to differentiate senders of incoming datagrams hey i am writing a gameserver query program. i need to request some information from 30000 servers. to do that i have created a socket, from which i broadcast packets to all the servers. so far so good… but when the servers respond, i need to determine which server the packet belongs to. it’s no problem getting the address of the datagram, but i can’t seem to get the portnumber i originally send to, and that is my big problem, since one address can host multiple games on different ports. me: ->> dgrequest( 27015 ) : them me: <<- dgresponse( 34532 ): them is it possible to get the destination port number of dgrequest from dgresponse? if not: is there no other possible solution than to create a socket for each server, and spawn a thread for each to retrieve the information? thanks !!! regards kimm stensborg comments (2) 20 jun peer to peer network persistent problems i am running windows 2000 on two systems in a peer-to-peer networks. the link is most unstable. for no apparent reason they lose each other, with "network path not found message" re-installing the tcp-ip protocols doesn’t seem to help. at times a disk share becomes available, but the internet shared connection is not. sending a console message from one to another seems to help sometimes to regain the disk shares, but the internet shared connection remains broken. i have followed the windows 2000 professional expert companion book advice to no avail and checked that all protocols needed are in place but something remains broken still. is there a troubleshooting process documented anywhere that can help me fix this for good? thanks comments (3) 20 jun multi network routing i am looking for how to set up the routing tables properly for the following situation. server1 (ip 192.168.254.140 gw 192.168.254.254)is connected to a dsl(ip 192.168.254.254, gw dynamic) router . connection 2 out of server1 is ip 10.0.0.2 gw 192.168.254.140. connection 2 connects to a wireless access point (ap) (ip 10.0.0.1 gw 10.0.0.2). client a (ip 10.0.0.34) connects to the ap and connects to the internet just fine. client a also has a ethernet card (ip 192.168.1.1 gw 10.0.0.34) which is directly connected to an ethernet device c (ip 192.168.1.2) via a crossover cable. what is required to allow ethernet device c to connect to server 1 and access the internet? comment (1) 20 jun lan set up problem hello, i am setting up a lan of 3 pc boxes & 2 unix freebsd’s, smc barricade router & hub. the unix – pc interactions to use samba, no problem expected there, had it set up before. the 3 pc’s, 2 wins2000 professional. & 1 win98. all pc’s shows the correct ip settings from ipconfig, with respect to ip address; subnet mask & default gateway. i can ping from each to each with a typical < 10 ms signal return. a "tracert" shows again < 10 ms signal to target machine in 1 hop the problem : despite this apparent symmetrical interaction, one of the win2000 machine does not share it’s files with the otherwin2000 machine, but shares files with the win98 pc. off course file sharing is set for all disks, could someone identify the problem and a fix. thanks – adam – ps: pl. reply to group comments (2) 20 jun adventures with closesocket() hi, i know this has been a problem for people in the past, but i’ll see if anyone has any new ideas. basically if i write an extremely simple server that simply sends back about ~40k of data back to the client and then closes the socket, then the connection is closed before sending all the data. if i add the following code before closing: fd_set fds; fd_zero(&fds); fd_set(m_handle, &fds); sleep(0); ::select(m_handle + 1, 0, &fds, 0, 0); sleep(0); shutdown(m_handle, sd_send); sleep(0); ::closesocket(m_handle); i can get ie to receive the entire data, but telnet doesn’t (this is on w2k btw). if i remove a single line of code from above it stops working for ie. i’ve tried every possible linger option with no luck. i’ve tried wsaeventselect on fd_close, no luck. the only thing that works for telnet is a hard-coded sleep for a considerable period (4-5 seconds). now it may be a bug in telnet: if i telnet to iis and retrieve a document of a similar size, then data is also lost (providing you don’t have connection: keep-alive). i’ve never seen this problem with ie but it still seems strange i need so much code just to get a graceful socket closure. any clues? dylan comment (1) 20 jun how to differentiate senders of incoming datagrams hey i am writing a gameserver query program. i need to request some information from 30000 servers. to do that i have created a socket, from which i broadcast packets to all the servers. so far so good… but when the servers respond, i need to determine which server the packet belongs to. it’s no problem getting the address of the datagram, but i can’t seem to get the portnumber i originally send to, and that is my big problem, since one address can host multiple games on different ports. me: ->> dgrequest( 27015 ) : them me: <<- dgresponse( 34532 ): them is it possible to get the destination port number of dgrequest from dgresponse? if not: is there no other possible solution than to create a socket for each server, and spawn a thread for each to retrieve the information? thanks !!! regards kimm stensborg comments (2) 20 jun peer to peer network persistent problems i am running windows 2000 on two systems in a peer-to-peer networks. the link is most unstable. for no apparent reason they lose each other, with "network path not found message" re-installing the tcp-ip protocols doesn’t seem to help. at times a disk share becomes available, but the internet shared connection is not

URL analysis for windowstcpip.info


http://www.windowstcpip.info/2011/05
http://www.windowstcpip.info/2010/07
http://www.windowstcpip.info/lan-set-up-problem-45
http://www.windowstcpip.info/lan-set-up-problem-46
http://www.windowstcpip.info/multi-network-routing-32#comments
http://www.windowstcpip.info/how-to-differentiate-senders-of-incoming-datagrams-39#comments
http://www.windowstcpip.info/page/2
http://www.windowstcpip.info/2010/03
http://www.windowstcpip.info/2010/02
http://www.windowstcpip.info/2010/05
http://www.windowstcpip.info/2010/06
http://www.windowstcpip.info/2013/03
http://www.windowstcpip.info/2011/09
http://www.windowstcpip.info/2011/06
http://www.windowstcpip.info/2010/08

Whois Information


Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain Name: WINDOWSTCPIP.INFO
Registry Domain ID: D35331727-LRMS
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: http://www.godaddy.com
Updated Date: 2016-11-14T07:11:32Z
Creation Date: 2010-11-07T19:42:50Z
Registry Expiry Date: 2018-11-07T19:42:50Z
Registrar Registration Expiration Date:
Registrar: GoDaddy.com, LLC
Registrar IANA ID: 146
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +1.4806242505
Reseller:
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registry Registrant ID: C96486103-LRMS
Registrant Name: Vladimir Melnikoff
Registrant Organization:
Registrant Street: Terekhov bulvar, 2
Registrant City: Moscow
Registrant State/Province:
Registrant Postal Code: 334013
Registrant Country: RU
Registrant Phone: +7.4954439418
Registrant Phone Ext:
Registrant Fax:
Registrant Fax Ext:
Registrant Email: [email protected]
Registry Admin ID: C96486126-LRMS
Admin Name: Vladimir Melnikoff
Admin Organization:
Admin Street: Terekhov bulvar, 2
Admin City: Moscow
Admin State/Province:
Admin Postal Code: 334013
Admin Country: RU
Admin Phone: +7.4954439418
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email: [email protected]
Registry Tech ID: C96486116-LRMS
Tech Name: Vladimir Melnikoff
Tech Organization:
Tech Street: Terekhov bulvar, 2
Tech City: Moscow
Tech State/Province:
Tech Postal Code: 334013
Tech Country: RU
Tech Phone: +7.4954439418
Tech Phone Ext:
Tech Fax:
Tech Fax Ext:
Tech Email: [email protected]
Registry Billing ID: C96486135-LRMS
Billing Name: Vladimir Melnikoff
Billing Organization:
Billing Street: Terekhov bulvar, 2
Billing City: Moscow
Billing State/Province:
Billing Postal Code: 334013
Billing Country: RU
Billing Phone: +7.4954439418
Billing Phone Ext:
Billing Fax:
Billing Fax Ext:
Billing Email: [email protected]
Name Server: NS1.4-DOS.INFO
Name Server: NS2.4-DOS.INFO
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2017-11-06T00:08:00Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to AFILIAS WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Afilias registry database. The data in this record is provided by Afilias Limited for informational purposes only, and Afilias does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Afilias reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

  REFERRER http://whois.afilias.info

  REGISTRAR Afilias Global Registry Services

SERVERS

  SERVER info.whois-servers.net

  ARGS windowstcpip.info

  PORT 43

  TYPE domain

DOMAIN

  NAME windowstcpip.info

  HANDLE D35331727-LRMS

  CREATED 2010-07-11

STATUS
clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
clientRenewProhibited https://icann.org/epp#clientRenewProhibited
clientTransferProhibited https://icann.org/epp#clientTransferProhibited
clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

NSERVER

  NS1.4-DOS.INFO 95.169.185.14

  NS2.4-DOS.INFO 95.169.185.14

OWNER

  HANDLE C96486103-LRMS

  NAME Vladimir Melnikoff

ADDRESS

STREET
Terekhov bulvar, 2

  CITY Moscow

  PCODE 334013

  COUNTRY RU

  PHONE +7.4954439418

  EMAIL [email protected]

ADMIN

  HANDLE C96486126-LRMS

  NAME Vladimir Melnikoff

ADDRESS

STREET
Terekhov bulvar, 2

  CITY Moscow

  PCODE 334013

  COUNTRY RU

  PHONE +7.4954439418

  EMAIL [email protected]

TECH

  HANDLE C96486116-LRMS

  NAME Vladimir Melnikoff

ADDRESS

STREET
Terekhov bulvar, 2

  CITY Moscow

  PCODE 334013

  COUNTRY RU

  PHONE +7.4954439418

  EMAIL [email protected]

BILLING

  HANDLE C96486135-LRMS

  NAME Vladimir Melnikoff

ADDRESS

STREET
Terekhov bulvar, 2

  CITY Moscow

  PCODE 334013

  COUNTRY RU

  PHONE +7.4954439418

  EMAIL [email protected]

  REGISTERED yes

Go to top

Mistakes


The following list shows you to spelling mistakes possible of the internet users for the website searched .

  • www.uwindowstcpip.com
  • www.7windowstcpip.com
  • www.hwindowstcpip.com
  • www.kwindowstcpip.com
  • www.jwindowstcpip.com
  • www.iwindowstcpip.com
  • www.8windowstcpip.com
  • www.ywindowstcpip.com
  • www.windowstcpipebc.com
  • www.windowstcpipebc.com
  • www.windowstcpip3bc.com
  • www.windowstcpipwbc.com
  • www.windowstcpipsbc.com
  • www.windowstcpip#bc.com
  • www.windowstcpipdbc.com
  • www.windowstcpipfbc.com
  • www.windowstcpip&bc.com
  • www.windowstcpiprbc.com
  • www.urlw4ebc.com
  • www.windowstcpip4bc.com
  • www.windowstcpipc.com
  • www.windowstcpipbc.com
  • www.windowstcpipvc.com
  • www.windowstcpipvbc.com
  • www.windowstcpipvc.com
  • www.windowstcpip c.com
  • www.windowstcpip bc.com
  • www.windowstcpip c.com
  • www.windowstcpipgc.com
  • www.windowstcpipgbc.com
  • www.windowstcpipgc.com
  • www.windowstcpipjc.com
  • www.windowstcpipjbc.com
  • www.windowstcpipjc.com
  • www.windowstcpipnc.com
  • www.windowstcpipnbc.com
  • www.windowstcpipnc.com
  • www.windowstcpiphc.com
  • www.windowstcpiphbc.com
  • www.windowstcpiphc.com
  • www.windowstcpip.com
  • www.windowstcpipc.com
  • www.windowstcpipx.com
  • www.windowstcpipxc.com
  • www.windowstcpipx.com
  • www.windowstcpipf.com
  • www.windowstcpipfc.com
  • www.windowstcpipf.com
  • www.windowstcpipv.com
  • www.windowstcpipvc.com
  • www.windowstcpipv.com
  • www.windowstcpipd.com
  • www.windowstcpipdc.com
  • www.windowstcpipd.com
  • www.windowstcpipcb.com
  • www.windowstcpipcom
  • www.windowstcpip..com
  • www.windowstcpip/com
  • www.windowstcpip/.com
  • www.windowstcpip./com
  • www.windowstcpipncom
  • www.windowstcpipn.com
  • www.windowstcpip.ncom
  • www.windowstcpip;com
  • www.windowstcpip;.com
  • www.windowstcpip.;com
  • www.windowstcpiplcom
  • www.windowstcpipl.com
  • www.windowstcpip.lcom
  • www.windowstcpip com
  • www.windowstcpip .com
  • www.windowstcpip. com
  • www.windowstcpip,com
  • www.windowstcpip,.com
  • www.windowstcpip.,com
  • www.windowstcpipmcom
  • www.windowstcpipm.com
  • www.windowstcpip.mcom
  • www.windowstcpip.ccom
  • www.windowstcpip.om
  • www.windowstcpip.ccom
  • www.windowstcpip.xom
  • www.windowstcpip.xcom
  • www.windowstcpip.cxom
  • www.windowstcpip.fom
  • www.windowstcpip.fcom
  • www.windowstcpip.cfom
  • www.windowstcpip.vom
  • www.windowstcpip.vcom
  • www.windowstcpip.cvom
  • www.windowstcpip.dom
  • www.windowstcpip.dcom
  • www.windowstcpip.cdom
  • www.windowstcpipc.om
  • www.windowstcpip.cm
  • www.windowstcpip.coom
  • www.windowstcpip.cpm
  • www.windowstcpip.cpom
  • www.windowstcpip.copm
  • www.windowstcpip.cim
  • www.windowstcpip.ciom
  • www.windowstcpip.coim
  • www.windowstcpip.ckm
  • www.windowstcpip.ckom
  • www.windowstcpip.cokm
  • www.windowstcpip.clm
  • www.windowstcpip.clom
  • www.windowstcpip.colm
  • www.windowstcpip.c0m
  • www.windowstcpip.c0om
  • www.windowstcpip.co0m
  • www.windowstcpip.c:m
  • www.windowstcpip.c:om
  • www.windowstcpip.co:m
  • www.windowstcpip.c9m
  • www.windowstcpip.c9om
  • www.windowstcpip.co9m
  • www.windowstcpip.ocm
  • www.windowstcpip.co
  • windowstcpip.infom
  • www.windowstcpip.con
  • www.windowstcpip.conm
  • windowstcpip.infon
  • www.windowstcpip.col
  • www.windowstcpip.colm
  • windowstcpip.infol
  • www.windowstcpip.co
  • www.windowstcpip.co m
  • windowstcpip.info
  • www.windowstcpip.cok
  • www.windowstcpip.cokm
  • windowstcpip.infok
  • www.windowstcpip.co,
  • www.windowstcpip.co,m
  • windowstcpip.info,
  • www.windowstcpip.coj
  • www.windowstcpip.cojm
  • windowstcpip.infoj
  • www.windowstcpip.cmo
Show All Mistakes Hide All Mistakes