Tag Info

Hot answers tagged

5

I think it's actually more debated than you make it appear. There is an admittedly old, related Linux FAQ: http://www.tldp.org/HOWTO/VPN-HOWTO/ I've used a PPP-over-ssh-over-ADSL for more than 12 years, and it never failed me, so from my experience I'd dare to say that the doomsayers probably largely exaggerate. TCP over TCP is probably a bad idea with RTC ...


3

Use netstat -ba in administrator level command prompt, and you will see all active network sockets and processes that own those sockets. -b tells netstat to output executable name of the socket owner. -a tella netstat to list all listening and client sockets.


3

Transaction (Process ID 65) was deadlocked on lock resources This is the problem... Also, the first 6 words of the error message. It's likely a race condition in your program's database access that results in the deadlock. It may also be a stale lock on the database; it's hard to tell. Queries that lock anything should be grouped in a transaction or at ...


2

See Shane Madden's answer. Also note that Wireshark doesn't add numbers to get that length, it gets the number from libpcap/WinPcap, which gets it from the underlying capture mechanism, which usually gets the number from the device driver, which typically gets it from the hardware. On Ethernet, the preamble and SOF delimiter are rarely captured (I don't ...


2

It's the count of the bytes that were captured for that particular frame; it'll match the number of bytes of raw data in the bottom section of the wireshark window. The contents of the capture depend on how the capture was done, but typically a capture grabs from the start of the header to the end of the payload. Click on the decoded protocol parts in the ...


1

Check is IIS is running. IIS uses kernel-level driver (http.sys) to handle http requests, so it's not displayed correctly in netstat. If it's there, check what site binds to :8080.


1

Port 8080 is a fairly commonly used port for Java apps. Either via Tomcat or Jetty. My bet would be Tomcat. Since this is a server & you clearly cannot access the content on port 8080, then my suggestion would be to look through your process list for anything Java related. Possibly also check the contents on ports 8081 as well as port 8000.


1

If your relay machine is running Linux or any UNIX-like OS, you can use socat (http://www.dest-unreach.org/socat/, it is included as a package in many Linux distributions). In its simplest form, you can start the relay with something like: socat TCP4-LISTEN:12345 TCP4-LISTEN:54321 (where 12345 and 54321 are the ports on which the server listens for each ...


1

This question is three years old but I feel it should be answered: they aren't open in the default installation; at least, not anymore. A port scan on a base installation of OpenBSD 5.5 only shows ssh: Port Scan has started… Port Scanning host: 192.168.1.29 Open TCP Port: 22 ssh Port Scan has completed… Enabling httpd and disabling pf ...


1

That log screams, to me, of either a cabling problem or a duplex mismatch between a device and the switch. I'd consider forcing the speed / duplex on the NICs on two devices (the server and a client) to 100Base-TX half-duplex and working up from there. Shoddy patch cables, bad NIC drivers, or a failing switch could cause these behaviors, too. It's important ...



Only top voted, non community-wiki answers of a minimum length are eligible